Configuring Feature Flags

Note: Spartacus 4.x is no longer maintained. Please upgrade to the latest version.

Note: Spartacus 4.x was tested with SAP Commerce Cloud versions 1905 to 2205. Spartacus 4.x has not been verified to work with (and is not guaranteed to work with) SAP Commerce Cloud 2211 or later releases.

Note: This feature is introduced with version 1.1 of the Spartacus libraries.

Each minor version of the Spartacus libraries includes new features, which are often improvements to existing components. These features are usually expected by users, but in some cases, these updates could be considered breaking changes, especially when you have built your own customizations on top of specific behaviors, or on top of the DOM structure.

Table of Contents

• Feature Levels
• Feature Flags

Feature Levels

To maintain strict backwards compatibility, Spartacus includes configurable feature levels, which help to maintain predictable behavior while improving existing components.

By default, the feature level is set to the latest major version (such as 1.0). To make use of new behaviors and improvements introduced in a minor version (such as 1.3), you can configure the feature level as shown in the following example:

{
  features: {
    level: '1.3'
  }
}

Note: Each consecutive feature level contains all of the features from the previous feature level.

If you want your feature level to always be set to the most recent version, you can use the latest flag ('*'), as follows:

features: {
  level: '*'
}

You can also disable a feature for a specific feature level by including an exclamation mark (!) before the version number. The following is an example:

<newComponent *cxFeatureLevel="'!1.1'"></newComponent>

Feature Flags

Some important features can be selectively toggled using specific feature flags.

The following is an example:

{
  features: {
    someFeature: false
  }
}

Feature flags can be linked to feature levels, which results in a feature being enabled by default if the defined feature level is available.

You can configure the feature level and feature flags at the same time, as shown in the following example:

{
  features: {
    level: '1.1',
    feature1: false,
    feature2: true
  }
}

In this example, the feature level is set to 1.1. With feature1 set to false, if feature1 is normally a part of the version 1.1 feature set, you can selectively disable this feature while keeping the rest of the features from the 1.1 release. If feature2 is part of the 1.5 release, by setting it to true, you can enable it while otherwise only enabling the features from the 1.1 release.

Note: It is recommended that you pay extra attention to testing your application if you are selectively enabling features. Although feature flags are used for a number of different Spartacus features, there is no guarantee that all functionalities will work for all possible combinations of feature flags and feature levels.